Print

The latest release information for the Active Directory module.

1.  Release History

December 13, 2012

Sitecore Active Directory module v1.0.4 rev. 121120 is released.

Tested with Sitecore CMS 6.5.0 rev. 120706 (Update-5) and Sitecore CMS 6.6.0 rev 121015 (Update-1).

Compatibility
This version of the module only runs on Sitecore 6.5 or later.

Change log.

Issues Resolved

• An issue when the LDAPLogin page didn’t respect the ClientLanguage has been fixed. (343685)
• An issue that caused an exception on the /sitecore/login/ page when IncludeIndirectMembership=true has been fixed. (356142)
• An issue that caused an exception when the module connected to Active Directory (AD) in a different domain has been fixed. (356601)
• An issue when the roles cache was not cleared for changes in nested domain containers has been fixed. (376014)

October 20, 2011

Active Directory module v1.0.3 rev.111005 is released.

Tested with Sitecore 6.6.0 rev. 121015.

Compatibility
The Active Directory module v1.0.3 rev.111005 is compatible with Sitecore CMS 6.x. This version is not compatible with the Sitecore CMS versions earlier than 6.x.

Change log.

Improvements:

• All three providers allow reading a username from the AD properties different from ‘sAMAccountName’. See the “Config file changes” section in the documentation for more details.
  • The user has to explicitly set the "attributeMapUsername" property to "userPrincipalName" for the corresponding AD Membership/Role/Profile providers if you use "userPrincipalName" as the user names.
  • The user has to explicitly set the "attributeMapUsername" property to "sAMAccountName" for the corresponding AD Membership/Role/Profile providers if you use "sAMAccountName" as the user names.
• The following changes are added to the module’s documentation:
  • minimal set of properties AD objects that have to be integrated into Sitecore security was added.
  • The Extending the Sitecore Template section was changed.
  • an additional property for security providers were added.
• Now users are allowed to provide a custom filter that will be applied to all requests to the AD server (also added to the documentation).

Issues resolved:

• The port 445 is no longer required to be opened to connect to AD domain with Active Directory module. (322971)
• An issue that caused User Manager to hang when the user was not logged in as an Admin AD-User has been fixed. (313169)
• An issue limiting the “members” or “membersOf” attributes in the Role Manager to 1500 objects has been fixed. (314630)
• An issue that causes an exception when Sitecore starts up if the AD server is unavailable has been fixed. (312754) 
• An issue with the configuration of the profile section causing an error on ProviderStatus.html page has been fixed. (330060)

June 8, 2011

Active Directory module v1.0.2 rev.090914 was tested with Sitecore CMS 6.5.0 rev.110602.

September 23, 2009

Active Directory module v1.0.2 rev.090914 is released.

Tested with Sitecore CMS 6.1.0 rev.090821.

Change log.

New features:

1. Significant performance improvements.
2. Introduces two special parameters in the LDAP.config file which influence the number of objects in User Manager:
   • LDAP.SizeLimit sets the number of returned user for “*” search pattern. It influences paging, getting all users (all API using GetAllUsers, FindUsersByName methods of SitecoreMembershipProvider).
   • LDAP.FindSizeLimit sets the number of returned users for the rest of search patterns. It influences custom search operations(all API using FindUsersByName, FindUsersByEmail methods of SitecoreMembershipProvider).

   I.e. LDAP.SizeLimit  directly affects the number of objects shown in User Manager. You can still search in User Manager to find the necessary users and the scope of search will not be limited to that setting. However the number of objects this operation will return will be no more than the value of the LDAP.FindSizeLimit setting for each domain.

3. No need of changing the Active Directory policy (MaxTempTableSize attribute).
4. Simplified configuration. No need to replace UserProfile class and SwitchingProfileProvider.
5. The Active Directory security provider now works in environments leveraging SQLite databases.
6. The Active Directory security provider no longer requires connection credentials in configuration files.

Issues resolved:

1. In some cases when displaying users stored in an Active Directory domain, the User Manager’s user list displayed an error when attempting to scroll to the last page of users.
2. The User Manager discarded changes to e-mail and comment fields of Active Directory users.
3. The timeout alert could occur in the User Manager when the searching for users in an Active Directory domain containing more than 1 million users.
4. An exception could occur when try to assign a role from an Active Directory domain to an Active Directory user in the User Manager.
5. Attempting to delete an Active Directory user that was not the member of an Organization Unit displayed an error.
6. The Active Directory security provider may not have been thread-safe.
7. The User Manager discarded changes to user properties added manually to the to the user profile template.

March 17, 2009

Active Directory module v1.0.1 rev.090302 is released.

Tested with Sitecore CMS 6.0.1 rev.090212.

Change log.

Issues fixed:

1. Fixed: Performance might decrease during logging in and anonymous site browsing operations with a high number of users in Active Directory domain.
2. Fixed: User Manager could not be opened if AD domain contained more than 1000000 users.
3. Fixed: When two logged in users opened the User Manager and worked with it (search, switch to the next page etc.), one user could receive requested data of another user.
4. Fixed: Error might occur when searching for AD users in the User Manager if the following was set in the ldap.config file: “LDAP.Sync = true”.
5. Fixed: If there were slashes (“/”) in AD common names for users, these users would not be found during user editing.
6. Fixed: Performance of Sitecore CMS with AD module installed is highly increased now.

September 16, 2008 

Active Directory module v1.0.0 rev.080903 is released.

Tested with Sitecore CMS 6.0.0 rev.080820 (aka Update-2).

Change log.

Issues fixed: 

1. AD user could be not found in a role.
2. When an AD user was assigned to an AD group and this group was specified as a primary role, it was not possible to edit the user and other AD roles could disappear from the user’s membership.
3. Provider status could be shown incorrectly.
4. Documentation was updated to point the .NET limitations.

New features:

1. Display Name attribute from the AD module can now be mapped to the Full Name property in Sitecore CMS.
2. The profile item can be assigned automatically to all users which come from the AD domain.
3. A better way to login and redirect users was implemented.

July 01, 2008 

Active Directory module v1.0.0 rev.080627 is released.

Tested with Sitecore CMS 6.0.

2.  Known issues

The list of known issues present in the latest version of the Active Directory module.

1. When the AD server name starts with “dc” or “DC” in the AD connection string, as in: 
   
   <add name="ManagersConnString" connectionString="LDAP://dctest/DC=company,DC=net "/>
   
   the AD module writes errors to the log file:
   
   1320 12:18:00 WARN  AD: reconnected
   1320 12:18:00 WARN  AD : attempt reconnecting...
   1320 12:18:10 WARN  AD: reconnected
   1320 12:18:10 WARN  AD : attempt reconnecting...
   1320 12:18:20 WARN  AD: reconnected
   1320 12:18:20 WARN  AD : attempt reconnecting...
   
   Workaround:
   Use the server IP instead of the server name in the AD connection string:
   
   <add name="ManagersConnString" connectionString="LDAP://[IP]/DC=company,DC=net "/>
   
   [IP] is the IP of the AD server, e.g. 127.0.0.1
   The AD connection string is placed in the App_Config/ConnectionStrings.config file.
2. If you have written custom code that calls the Active Directory module’s API, you may encounter compilation errors (“missing assembly”) when you upgrade to the latest version.  This could happen due to a change in the assembly version between the previous and latest module versions. 
   Workaround:
   To work around this issue, re-reference the [module] assembly as a version independent reference (specific version = “false”) and recompile your code.
3. An exception may occur when changing the profile of an Active Directory user created in Sitecore.
   Workaround:
   Open the /App_Config/Security/Domains.config.xml file and add the following line to the domains element:
   
   <domain name="ad" ensureAnonymousUser="false" defaultProfileItemID="{DDEDA46F-169B-4A70-8732-DBD3F407AF2E}"/>
   The defaultProfileItemID attribute defines the profile item that will be used for users from the domain if the profile is not set for the user explicitly.
4. The first installation of the module package may fail without any exact error description.
   Workaround:
   Install the package again (use the appropriate button on the last wizard screen) and choose Overwrite option for all files. 
5. The AD module doesn't support the SSL protocol.